The error message indicates an AIX software issue or AIX software assistance
required.. The reason code
(0xBBBB BBBB) field may contain additional informatIOn. Whenever these errors are encountered,
AIX support should be contacted.
Error code | Meaning | Action |
0x0000 0005 | The AIX protocol driver has received a clear queue request with no associated SCSI command. | This is an AIX issue, contact AIX SAN support |
0x0000 0006 | The AIX protocol driver command completion processor has received an IOCB that it does not know how to process. | This may indicate a corrupted command ring, contact AIX SAN support |
0x0000 0007 | A cancel command has failed | This is an AIX issue, contact AIX SAN support |
0x0000 0008 | Invalid cmd type for cancel completed. | This is an AIX issue, contact AIX SAN support |
0x0000 0016 | ||
0x0000 0046 | The adapter has rejected an IOCB from the AIX device driver because it was invalid | This is an AIX issue, contact AIX SAN support |
0x0000 004e | An application/AIX hdisk/tape driver is requested a start device and is use an incorrect world wide name or node name. | This is an AIX issue, contact AIX SAN support |
0x0000 0051 | The AIX device driver returned an error for a Cancel command sent by the the AIX protocol driver. | This is AIX issue, contact AIX SAN support. |
0x0000 0072 | The IO tag the AIX protocol driver used in the IOCB does not match the IO tag in the AIX ctl_elem structure. This is a corrupted IOCB. a corrupted AIX ctl_elem structure. | Contact AIX SAN support. |
0x0000 00a4 | The AIX device driver has sent an unknown command to the AIX protocol driver | This is AIX issue, contact AIX SAN support. |
0x0000 00ab | On get port ID request, the buffer to hold the ID was not large enough | This is an AIX issue, contact AIX support. |
0x0000 00b3 | With AIX dynamic tracking enabled, the scsi buffer passed to the AIX protocol driver from the head drive did not set the kernext_handle field. | Contact AIX SAN support |
0x0000 00b9 | Following an AIX dynamic tracking event, the AIX target information and AIX device informatIOn are out of sync. | Contact AIX SAN support |
0x0000 00be | The rpi returned for a move_login operation was 0 and the AIX device driver returned a good status. | In sufficient info logged with this error message, Contact AIX SAN support. |
0x0000 00bf | Following a AIX protocol start request, the World Wide Name and/or node name fields in the AIX target informatIOn and the AIX scsi IO list structure.do match. | Contact AIX SAN support |
0x0000 00c2 | An attempt to add a AIX target info to an AIX hash table found the target info already in the table | If this issue persists, contact AIX SAN support |
0x0000 00c5 | There were multiple AIX matches for AIX device info lookup in AIX structures and a unique match could not be made | If this issue persists, contact AIX SAN support |
0x0000 00c9 | Following a dynamic tracking event. an AIX request was received by the AIX protocol driver and the requested world wide name and/or node name fields did not match the info in the AIX target info. (Following a change in the SAN, and a dynamic tracking operatIOn to handle the change, not all AIX structure have been updated). | Contact AIX SAN support. |
0x0000 00cc | A AIX request to the AIX protocol driver has failed due to setup info structure inconsistencies. | Contact AIX SAN support |
0x0000 00cf | A scsi id (N_Port ID) change was detected on an AIX request to the AIX protocol driver that did not have the world wide name set and there was no dynamic tracking event. This is an AIX driver programming error... | Contact AIX SAN support |
0x0000 00d0 | The AIX protocol driver received an AIX scsi buffer without a command length specified. | Contact AIX SAN support |
0x0000 00d1 | The AIX protocol driver received a interrupt for a command that was not active | Contact AIX SAN support |
0x0000 00d2 | An AIX scsi buffer was passed to the AIX protocol driver with a kernel extension handle field that had an invalid value | Contact AIX SAN support |
0x0000 00d4 | An AIX disk driver sent a request to the AIX protocol driver fields in the request were not set or were invalid | Contact AIX SAN support |
0x0000 00d5 | A move login was sent to the AIX protocol driver with a error in the AIX target info structure | Contact AIX SAN support |
0x0000 00d7 | An AIX timer has been started for a dynamic tracking event, but no dynamic events are in progress. | Contact AIX SAN support |
0x0000 00d8 | While processing a State Change Notification, a dynamic tracking timer was set, but no dynamic tracking operations were in progress. | Contact AIX SAN support |
0x0000 00da | While processing a logout a dynamic tracking timer was set, but no dynamic tracking operations were in progress | Contact AIX SAN support |
0x0000 00dd | Attempted AIX search for target informatIOn., but the required AIX search informatIOn was not provided | Contact AIX SAN support |
0x0000 00de | The AIX protocol driver received an AIX request without a device restart command | Contact AIX SAN support |
0x0000 00f0 | The AIX protocol driver has received a request from an AIX hdisk driver that had an unsupported scsi buffer. | Contact AIX SAN support |
0x0000 00f1 | The AIX protocol driver was unable to get AIX memory for an AIX event buffer. | Contact AIX SAN support |
0x0000 0011 0x0000 0012 0x0000 0013 0x0000 0043 0x0000 0050 0x0000 0053 0x0000 0054 0x0000 0055 0x0000 0056 0x0000 0057 0x0000 0058 0x0000 0059 0x0000 005a 0x0000 005b 0x0000 005c 0x0000 005d 0x0000 005e 0x0000 005f 0x0000 0063 0x0000 0064 0x0000 0074 0x0000 0075 0x0000 0076 0x0000 0077 0x0000 0078 0x0000 0079 0x0000 007d 0x0000 007e 0x0000 007f 0x0000 0080 0x0000 0081 0x0000 0083 0x0000 0084 0x0000 0085 0x0000 0086 0x0000 0087 0x0000 0088 0x0000 0089 0x0000 008a 0x0000 008b 0x0000 008c 0x0000 008d 0x0000 008e 0x0000 008f 0x0000 0090 0x0000 0091 0x0000 0092 0x0000 0093 0x0000 0094 0x0000 0095 0x0000 0096 0x0000 0097 0x0000 0098 0x0000 0099 0x0000 009a 0x0000 009b 0x0000 009c 0x0000 009e 0x0000 009f 0x0000 00e0 0x0000 00f2 0x0000 00f3 0x0000 00f4 0x0000 00f5 0x0000 00f6 0x0000 00f9 0x0000 00fa 0x0000 00fb 0x0000 00fc 0x0000 00fd 0x0000 00fe 0x0000 00ff 0x0000 0101 0x0000 0104 0x0000 0106 0x0000 0107 0x0000 010a 0x0000 010b 0x0000 010d 0x0000 010f 0x0000 0120 0x0000 0121 0x0000 0122 0x0000 0123 0x0000 0124 0x0000 0125 0x0000 0125 |
AIX device driver data structure eyecatcher check failed, this indicates an invalid or corrupted internal AIX data structure. | These are AIX issues, contact AIX SAN support. |
Detail Data SENSE DATA NOTE: Below is a portion of the AIX 5.3 and AIX 6.1 error templates. Click here to see full error template
AIX Version 5.3 and below
RRRR RRRR AAAA AAAA BBBB BBBB CCRR RRRR RRRR YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ GGGG GGGG OOOO OOOO OOOO OOOO EEEE EEEE
EEEE EEEE VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV
VVVV VVVV TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT
...continued...
AIX Version 6.1 and above
hhhh hhhh AAAA AAAA BBBB BBBB CCtt vvvv YYYY YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ
QQQQ QQQQ
GGGG GGGG pppp pppp OOOO OOOO OOOO OOOO EEEE EEEE EEEE EEEE ssss
ssss ssss ssss
wwww wwww wwww wwww nnnn nnnn nnnn nnnn nnnn qqqq qqqq qqqq
rrrr rrrr rrrr rrrr
MMNN PPSS UUWW XXZZ 11RR 2222 3333 3333 4444 4444 5555
5555 6666 6666 RRRR RRRR
7777 7777 8899 aabb cccc cccc dddd dddd eeee eeee
ffgg iijj mmnn ooRR JJJJ uuuu
%%%% %%%% %%%% %%%% &&&&
&&&& **** **** :::: :::: xxxx yyyy IIII IIII IIII IIII
VVVV
.... continued....